Changing layout of a second database

[Matt Jacobson-Carroll]

I have a problem I can't seem to think my way out of. I want to have a
user click on any one of 6 different buttons in one file and have it
open a second file and then switch to a corresponding layout.

When I try to use a script to copy the value of the button, the value
gets destroyed when opening up the second database (bug??). There
exists no relationship between the files, and I am not sure what I would
use for an ID field to create one.

Any ideas?

Thanks,

Matt

[Bridget Eley]

How is it that you are copying the value of the button? To my knowledge,
there is no way to do this without also copying the button itself. If you
paste the copied button onto another layout, the copied button should work
as well as the original. If you paste the button into another filemaker
file, the button will lose track of the original script it was attached to,
but you should be able to reformat it to a new script in the new file.

However, I am not sure why you would need to copy the buttons to the second
file.

Set up a go to layout script for each layout in the second file.

Setup up a script for each button in the first file which calls on the
corresponding Go to Layout script in the second file.

Create your buttons in the first file then format each to run the
appropriate script.

--
Bridget Eley

in article 20020801133...@news.gwi.net, Matt Jacobson-Carroll at
jaco...@bowdoin.edu wrote on 8/2/02 3:34 AM:

[Matt Jacobson-Carroll]

Bridget,

Thanks for your reply. Perhaps I didn't explain my situation clearly.
I am not trying to copy buttons, but to switch the layout of a second
database.

Here is what I am doing now (which isn't working). When the user clicks
on a button a script is run. That script puts a number into the
'clipboard'. The next step of the script opens another file and runs a
script in that file. That script uses the number in the clipboard to
switch to a specific layout. However it seems that Filemaker (or the OS?)
is not carrying the clipboard value to the second database. Running FM5.
5 on OSX.1.5

Thanks,

Matt

[Bridget Eley]

Is there a calculation involved in determining the layout number? If so,
set a global number field in the second file to the result using any
relationship (if there isn't one, create one based on a calc field in each
file = 1) then use the Go to Layout by field value option, referencing the
global number field.

If there is no calculation involved, if merely choosing the button tells you
which layout the user wants to go to, there is no reason to pass the number
at all. Use the method described in my previous post.

--
Bridget Eley

in article 20020801153...@news.gwi.net, Matt Jacobson-Carroll at
jaco...@bowdoin.edu wrote on 8/2/02 5:38 AM:

[Claude Carlos]

I'm not familiar with OSX , I work with windows XP.
Instead of using the clipboard, maybe you could use a global field ???

When the user clicks , that script could create a Global value (Define
Field,gLayoutNumber ),
then trough a relationship you could get that value in the script in the
second file .

Claude

"Matt Jacobson-Carroll" <jaco...@bowdoin.edu> a écrit dans le message de
news: 20020801153...@news.gwi.net...

[Matt Jacobson-Carroll]

Thanks Bridget. Works great.